Skip to content

Conversation

@wojiushixiaobai
Copy link

This commit fixes compatibility issues with wheels built for loongarch64
architecture that contain GLIBC_2.0 versioned symbols. The patch adds
GLIBC_2.0 to the allowed symbol versions for all loongarch64 manylinux
policies:

  • manylinux_2_36_loongarch64
  • manylinux_2_38_loongarch64
  • manylinux_2_39_loongarch64

Problem:
Wheel repair was failing with errors like:

"Package requires GLIBC_2.0, incompatible with policy manylinux_2_38_loongarch64"
This occurred because certain libraries (particularly libgcc_s.so.1) still
reference the legacy GLIBC_2.0 symbol version, which was not included in
the loongarch64 policy definitions.

Solution:
Add GLIBC_2.0 to the GLIBC symbol version whitelist for loongarch64
targets, matching the symbol version support already present in other
architecture policies.

This change enables successful wheel repair for packages containing
legacy GLIBC_2.0 symbols while maintaining compatibility with the
respective manylinux standards.

@codecov
Copy link

codecov bot commented Oct 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.22%. Comparing base (0d8470a) to head (77c8492).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #629      +/-   ##
==========================================
- Coverage   80.66%   79.22%   -1.44%     
==========================================
  Files          22       22              
  Lines        1815     1815              
  Branches      338      338              
==========================================
- Hits         1464     1438      -26     
- Misses        269      292      +23     
- Partials       82       85       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant